I have a network with 7 computers, all Win 7, most 64 bit Home Premium SP1, some 32bit. 4 over WIFI, the rest via gigabit ethernet. All (but one) computers work like you would expect - they can access all shared drives. The one I am having trouble with (64bit) can BE accessed from all other PCs and it does see all other computers on the network, however, it cannot access them, including ITSELF (in the network tab). I always get [computer] is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions. The network address is invalid. (When trying to connect to itself: A device attached to the system is not functioning.) All the shared drives are authorized for 'Everyone' with full control (read/write) TCP/IP V4 and V6 are active. The NetBIOS in the Advanced WINS is set to Default. I tried with identical user and password across the entire network. I tried without passwords. I tried the Homegroup, which again shows all the folders, but when I double click on them, nothing happens....

elwood0000 wrote: I have a network with 7 computers, all Win 7, most 64 bit Home Premium SP1, some 32bit. 4 over WIFI, the rest via gigabit ethernet. All (but one) computers work like you would expect - they can access all shared drives. The one I am having trouble with (64bit) can BE accessed from all other PCs and it does see all other computers on the network, however, it cannot access them, including ITSELF (in the network tab). I always get [computer] is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions. The network address is invalid. (When trying to connect to itself: A device attached to the system is not functioning.) All the shared drives are authorized for 'Everyone' with full control (read/write) TCP/IP V4 and V6 are active. The NetBIOS in the Advanced WINS is set to Default. I tried with identical user and password across the entire network. I tried without passwords. I tried the Homegroup, which again shows all the folders, but when I double click on them, nothing happens.... Have you tried to disable firewall on the problem PC completely for a test? Is the Workstation service running? Can you ping all other PCs from the problem PC? Wolfgang

Firewall is off on the problem PC. Workstation service is running. I can ping all other PCs via their IP address.

elwood0000 wrote: Firewall is off on the problem PC. Workstation service is running. I can ping all other PCs via their IP address. Can you ping them via name? If not - see if you have differences in the dns setup betwen the working PCs and the not working PC. Wolfgang

Can you ping them via name? If not - see if you have differences in the dns setup betwen the working PCs and the not working PC. Wolfgang Every computer can ping itself via name. The problem PC can ping every other computer on the network via name. The other computers can ping each other via name, but time out when pinging the problem computer.

elwood0000 wrote: Can you ping them via name? If not  - see if you have differences in the dns setup betwen the working PCs and the not working PC. Wolfgang Every computer can ping itself via name. The problem PC can ping every other computer on the network via name. The other computers can ping each other via name, but time out when pinging the problem computer.  That means, that the dns entry for your problem computer is wrong (or maybe missing) in your dns server database. If you look at the actual IP-address of your problem PC and the IP-address, which is used to ping it, you should see a discrepancy. Try to correct that and see, if this clears things. Wolfgang

elwood0000 wrote: That means, that the dns entry for your problem computer is wrong (or maybe missing) in your dns server database. If you look at the actual IP-address of your problem PC and the IP-address, which is used to ping it, you should see a discrepancy. Try to correct that and see, if this clears things. Wolfgang Hmmm.... They all show: (obtaining IP address and DNS server address automatically) IPv4 Address: 192.168.1.XX (XX ranges between 02 and 20) IPv4 Subnet Mask: 255.255.255.0 IPv4 Default Gateway: 192.168.1.254  IPv4 DHCP Server: 192.168.1.254   IPv4 DNS Server: 192.168.1.254                                192.168.1.254 IPv4 WINS Server NetBIOS over Tcpip Enabled: Yes What I did notice, however, is that when clicking on Advanced in the 'Internet Protocol Version 4 TCP/IPv4 Properties' that the 'Default gateways' field is empty, whereas it shows 192.168.1.254 on all other machines. If I do a manual add, nothing changes and when i return to the settings, it is blank again. I also assigned a static IP to the computer without result. Am I not looking in the right place?  That's not really what I wanted to know. If you ping your problem PC by name, what ip-address is shown as the one that is tried to get a reply from? If you enter "nslookup name of problem PC" what ip-address do you see below the Name entry? What is the actual ip-address of the problem PC? Those 3 values should be identical - if not that has to be addressed. Have you ever tried to access the shares on your problem PC via IP e.g. \\192.168.1.xx\sharename - and if it is not accessible that way, what error message do you get? What type of device is at the IP-address 192.168.1.254 is it a server, a hardware router and if it is the later is it in full control of you or is it (partially) controlled by your ISP. Lastly is the problem PC connected wirelessly or via ethernet cable to your LAN? Wolfgang

If you ping your problem PC by name, what ip-address is shown as the one that is tried to get a reply from? If you enter "nslookup name of problem PC" what ip-address do you see below the Name entry? What is the actual ip-address of the problem PC? Those 3 values should be identical - if not that has to be addressed. Have you ever tried to access the shares on your problem PC via IP e.g. \\192.168.1.xx\sharename - and if it is not accessible that way, what error message do you get? What type of device is at the IP-address 192.168.1.254 is it a server, a hardware router and if it is the later is it in full control of you or is it (partially) controlled by your ISP. Lastly is the problem PC connected wirelessly or via ethernet cable to your LAN? Wolfgang If i ping the problem PC by name from itself, it reports back with the IPv6 address. Its IPv4 address is 192.168.1.4. If i try to ping it from other computers they show 207.223.0.140 before they time out. If I do an nslookup by name of the problem PC from another PC, I get: Server: WL.hsd1.ga.comcast.net Address: 192.168.1.254 Non-authoritative answer: Name: problem-pc.Workgroup Address: 207.223.0.140 If I do an nslookup by name of the problem PC from itself, I get: Server: WL.hsd1.ga.comcast.net Address: 192.168.1.254 ***WL.hsd1.ga.comcast.net can't find elwood-pc: Non-existent domain If I try to access the problem PC via: \\192.168.1.4\problem-pc I get back: Windows cannot access \\192.168.1.4\problem-pc but I can access the problem PC just fine with name only (\\problem-pc) from any computer in the network. The device at 192.168.1.254 is a Belkin gigabit router, which is under my full control. The problem PC connects via cable. A DHCP Client list on the router shows all attached computers in the 192.168.1.XX range, including the problem PC at 192.168.1.4 So there is an apparent discrepancy with the two IP addresses, which confuses me even more, since the 'wrong' IP only shows up when pinging from other computers, but all other computers on the network can access the problem pc just fine. The problem pc cannot get to any of the other computers. If i do an ipconfig on the problem PC, it shows 192.168.1.4, with the default gateway being 192.168.1.254. Thanks for all your help.

elwood0000 wrote:   If you ping your problem PC by name, what ip-address is shown as the one that is tried to get a reply from? If you enter "nslookup name of problem PC" what ip-address do you see below the Name entry? What is the actual ip-address of the problem PC? Those 3 values should be identical - if not that has to be addressed. Have you ever tried to access the shares on your problem PC via IP e.g. \\192.168.1.xx\sharename - and if it is not accessible that way, what error message do you get? What type of device is at the IP-address 192.168.1.254 is it a server, a hardware router and if it is the later is it in full control of you or is it (partially) controlled by your ISP. Lastly is the problem PC connected wirelessly or via ethernet cable to your LAN? Wolfgang If i ping the problem PC by name from itself, it reports back with the IPv6 address. Its IPv4 address is 192.168.1.4. If i try to ping it from other computers they show 207.223.0.140 before they time out. If I do an nslookup by name of the problem PC from another PC, I get: Server: WL.hsd1.ga.comcast.net Address: 192.168.1.254 Non-authoritative answer: Name: problem-pc.Workgroup Address: 207.223.0.140 If I do an nslookup by name of the problem PC from itself, I get: Server: WL.hsd1.ga.comcast.net Address: 192.168.1.254 ***WL.hsd1.ga.comcast.net can't find elwood-pc: Non-existent domain If I try to access the problem PC via:  \\192.168.1.4\problem-pc I get back: Windows cannot access  \\192.168.1.4\problem-pc but I can access the problem PC just fine with name only (\\problem-pc) from any computer in the network. The device at 192.168.1.254 is a Belkin gigabit router, which is under my full control. The problem PC connects via cable. A DHCP Client list on the router shows all attached computers in the 192.168.1.XX range, including the problem PC at 192.168.1.4 So there is an apparent discrepancy with the two IP addresses, which confuses me even more, since the 'wrong' IP only shows up when pinging from other computers, but all other computers on the network can access the problem pc just fine. The problem pc cannot get to any of the other computers.  If i do an ipconfig on the problem PC, it shows 192.168.1.4, with the default gateway being 192.168.1.254. Thanks for all your help.  Can you give us in contrast the output of nslookup for the name of a problemless PC - maybe you have different parent domains/domain suffixes. Can you try to add a static dns record into your belkin router with the name of the problem pc and the address 192.168.1.4 and retry all tests. The IP-address 207.223.0.140 is apparently a search server of your ISP comcast, whereto non-resolvable names are redirected. To address a share I meant if you have created a share of e.g. C on your problem PC you would address that as \\Problem-PC\C and instead try \\192.168.1.4\C - of course \\192.168.1.4\Problem-pc does not exist. I think we are quite near to the solution. Wolfgang

Maybe - Client for Microsoft Networks is missing from the Network Connection Properties on the problem-pc ? I had a problem like yours and spent ages before finding the solution - all had been working well for months. How it had been removed/disbled I have yet to work out. HTH

Can you give us in contrast the output of nslookup for the name of a problemless PC - maybe you have different parent domains/domain suffixes. Can you try to add a static dns record into your belkin router with the name of the problem pc and the address 192.168.1.4 and retry all tests. The IP-address 207.223.0.140 is apparently a search server of your ISP comcast, whereto non-resolvable names are redirected. To address a share I meant if you have created a share of e.g. C on your problem PC you would address that as \\Problem-PC\C and instead try \\192.168.1.4\C - of course \\192.168.1.4\Problem-pc does not exist. I think we are quite near to the solution. Wolfgang All nslookups yield the exact same result: Server: WL.hsd1.ga.comcast.net Address: 192.168.1.254 ***WL.hsd1.ga.comcast.net can't find [ANY-PC]: Non-existent domain Not quite sure what you want me to do when you suggest to add a static DNS record - right now the router is set to get it automatically from the ISP - do you want me to actually turn that off and set it to 192.168.1.4 - or to 254? - you also mention the 'name' of the problem-pc, but there is no field for a name in the DNS section. If I try the \\192.168.1.4\xxxx, it will go straight to it on some shares and will give me a 'you do not have permission' on some others, though they are all shared in the same fashion.

Maybe - Client for Microsoft Networks is missing from the Network Connection Properties on the problem-pc ? I had a problem like yours and spent ages before finding the solution - all had been working well for months. How it had been removed/disbled I have yet to work out. HTH Oh how great that would have been...but unfortunately the Client for Microsoft Networks sits right there in the Local Area Connection Properties with its check-mark in place.....

elwood0000 wrote:   Can you give us in contrast the output of nslookup for the name of a problemless PC - maybe you have different parent domains/domain suffixes. Can you try to add a static dns record into your belkin router with the name of the problem pc and the address 192.168.1.4 and retry all tests. The IP-address 207.223.0.140 is apparently a search server of your ISP comcast, whereto non-resolvable names are redirected. To address a share I meant if you have created a share of e.g. C on your problem PC you would address that as \\Problem-PC\C and instead try \\192.168.1.4\C  - of course \\192.168.1.4\Problem-pc does not exist. I think we are quite near to the solution. Wolfgang All nslookups yield the exact same result: Server: WL.hsd1.ga.comcast.net Address: 192.168.1.254 ***WL.hsd1.ga.comcast.net can't find [ANY-PC]: Non-existent domain That's not the same you told me before because nslookup for your problem PC returned a wrong address (for Problem-pc.workgroup) but did answer the request. Not quite sure what you want me to do when you suggest to add a static DNS record - right now the router is set to get it automatically from the ISP - do you want me to actually turn that off and set it to 192.168.1.4 - or to 254? - you also mention the 'name' of the problem-pc, but there is no field for a name in the DNS section.  Don't do that. So from your tests it seems, that your router is not providing name resolution for your own local net. Is there a hosts file (usually under C:\Windows\system32\drivers\etc ), which contains entries for your other PCs ? Does "ping ANY-PC" ping the correct Ip-address of the ANY-PC or some other? If I try the \\192.168.1.4\xxxx, it will go straight to it on some shares and will give me a 'you do not have permission' on some others, though they are all shared in the same fashion. That's good news as it shows, that you can reach your PC if you enter the correct IP-address. The no permission problem is another one and has not necessarily anything to do with sharing settings but probably with the security settings for the shared folders. That you can deal with afterwards but first you have to get name resolution to work. I don't know your router - but look if you can set your router, so that it can act as a name-server for your local net not just as forwarder of name-server requests to your ISP. If you can do that, there is a database or list which contains the ip-address for each name in this list or database. This database or list you should populate with the corrrect entries for your local net and there I'd first start with the entry for your problem-PC. There are solutions, that your PCs register automatically with your name-server - but that question I can't answer as it has to be enabled on the name-server (router). The Windows part is easy - just check the "Register this connection's addresses in DNS" setting on the DNS tab of the TCP/IPv4 properties page. Wolfgang

That's not the same you told me before because nslookup for your problem PC returned a wrong address (for Problem-pc.workgroup) but did answer the request. well, the result was different before, because i did the nslookup for the problem pc. This time you asked me to do one for the non-problem pcs. I guess i should have clarified that it was [Any-PC, except problem PC] - the problem PC lookups still return what I told you earlier. "Register this connection's addresses in DNS" setting is already checked for the problem PC. Sounds like my best solution is to kick the router to the curb and get a cisco and start from scratch..... since i cannot find any name server function outside of the ISP thing.... thanks a ton for your help.

elwood0000 wrote: That's not the same you told  me before because nslookup for your problem PC returned a wrong address (for Problem-pc.workgroup) but did answer the request.   well, the result was different before, because i did the nslookup for the problem pc. This time you asked me to do one for the non-problem pcs. I guess i should have clarified that it was [Any-PC, except problem PC] - the problem PC lookups still return what I told you earlier. "Register this connection's addresses in DNS" setting is already checked for the problem PC. Sounds like my best solution is to kick the router to the curb and get a cisco and start from scratch..... since i cannot find any name server function outside of the ISP thing....   thanks a ton for your help.  The unanswered question remains, what ip-address is pinged, when you ping the non problem PCs by name is it the correct one or another one. Theoretically you don't need a name-server if you propagate the same hosts file to all PCs, which contains ip-address dns-names pairs for all your PCs. As the hosts file does override name-server lookups your internal name resolution would be independent of your ISP. Of course, whith a lot of PCs it gets quite complicated to update all hosts files simultaneously. If you don't want to spend extra money you could run a Linux virtual machine on one of your PCs, which is running named the Linux name-server daemon. That is pretty easy to setup and does not pose any heavy load on the PC hosting it. If you have any server already in place be it Windows, Linux, FreeBSD, Apple or any other OS I would put the name server functionality onto this server and probably the DHCP functionality, too. You don't need a Cisco router for name-server functionality, but even some of the cheap Ciscos do not include a name-server so you would have to look specifically at this functionality as a requirement. According to your nslookup results for the problem-pc you seem to have set a primary domain suffix of workgroup at your PCs, is this same setting also in place on the problem-PC? Wolfgang

I doubt the router is the problem - it just seems like the network adapter is struggling I suggest that you uninstall the adapter (from Device Manager) and then reboot the machine. Let it do a default reinstall so that the adapter is fully auto configured. (assuming it is not some exotic card or other hardware that you have) Good luck!

I doubt the router is the problem - it just seems like the network adapter is struggling I suggest that you uninstall the adapter (from Device Manager) and then reboot the machine. Let it do a default reinstall so that the adapter is fully auto configured. (assuming it is not some exotic card or other hardware that you have) Good luck! OK - thanks for hanging in there with me. Did some more things... still the same issues. As David suggested, I deleted the driver for the adapter off the computer, rebooted and re-downloaded the latest version (Broadcom). I also enabled an integrated WIFI adapter, which I had never used before to determine if maybe the NIC was the issue. I reset the Belkin router to factory default and it gave me a new set of IP addresses for the network. It now is 192.168.2.1 for the router, .2 for the problem PC, .3 and .4 for two working PCs and .9 for the WIFI of the problem PC. I left the other computers off the network for now and after confirming that .3 and .4 were working fine with each other, I also turned off .3. So for the tests I had: .1 router .2 problem pc NIC .9 problem pc WIFI .4 good pc I can ping any computer from any computer via IP address and via name, in which case it shows the IPv6 address. nslookup from any PC results in: Default Server: WL.hsd1.ga.comcast.net Address: 192.168.2.1 Trying to access the network from the problem PC: \\problem-pc - will show me all shared folders, but when I try to access one, it will give me the error: Network Error Windows cannot access \\problem-pc\Users Check the spelling of the name. Otherwise, there might be a problem with your network. To try to identify and resolve the problem, click Diagnose [Details: Error code: 0x80070035 The network Path was not found].... needless to say, Diagnose does not find any problems. \\192.168.2.2\ and \\192.168.2.2\Users will produce the same error. As does everything using .9 [wifi] instead. \\good-pc - will immediately give me an error: \\good-pc is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions. The network address is invalid. Trying to access the network from the good PC: \\good-pc and \\192.168.2.4 will get me to all shared folders and also lets me access them \\problem-pc and \\192.168.2.2 and .9 [wifi] will do the same thing Summary: The problem PC can be seen on and sees the entire network and can be accessed from the network, but cannot access anything on the network, including itself. Since the router works with all other computers, I doubt it is the problem, since the WIFI and the wired NIC behave the same way, I do not think either of those are the problem, either. Maybe it is 'something' telling me it is time to upgrade? :)

elwood0000 wrote: I doubt the router is the problem - it just seems like the network adapter is struggling I suggest that you uninstall the adapter (from Device Manager) and then reboot the machine. Let it do a default reinstall so that the adapter is fully auto configured. (assuming it is not some exotic card or other hardware that you have) Good luck! OK - thanks for hanging in there with me. Did some more things... still the same issues. As David suggested, I deleted the driver for the adapter off the computer, rebooted and re-downloaded the latest version (Broadcom). I also enabled an integrated WIFI adapter, which I had never used before to determine if maybe the NIC was the issue. I reset the Belkin router to factory default and it gave me a new set of IP addresses for the network. It now is 192.168.2.1 for the router, .2 for the problem PC, .3 and .4 for two working PCs and .9 for the WIFI of the problem PC. I left the other computers off the network for now and after confirming that .3 and .4 were working fine with each other, I also turned off .3. So for the tests I had: .1 router .2 problem pc NIC .9 problem pc WIFI .4 good pc  I can ping any computer from any computer via IP address and via name, in which case it shows the IPv6 address. nslookup from any PC results in: Default Server: WL.hsd1.ga.comcast.net Address: 192.168.2.1 Trying to access the network from the problem PC: \\problem-pc - will show me all shared folders, but when I try to access one, it will give me the error:  Network Error Windows cannot access \\problem-pc\Users Check the spelling of the name. Otherwise, there might be a problem with your network. To try to identify and resolve the problem, click Diagnose [Details: Error code: 0x80070035 The network Path was not found].... needless to say, Diagnose does not find any problems. \\192.168.2.2\ and \\192.168.2.2\Users will produce the same error. As does everything using .9 [wifi] instead. \\good-pc - will immediately give me an error: \\good-pc is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions. The network address is invalid.  Trying to access the network from the good PC: \\good-pc and \\192.168.2.4 will get me to all shared folders and also lets me access them \\problem-pc and \\192.168.2.2 and .9 [wifi] will do the same thing  Summary: The problem PC can be seen on and sees the entire network and can be accessed from the network, but cannot access anything on the network, including itself. Since the router works with all other computers, I doubt it is the problem, since the WIFI and the wired NIC behave the same way, I do not think either of those are the problem, either.  Maybe it is 'something' telling me it is time to upgrade? :) Okay I think it is time to start packet captures. Download MS Network Monitor http://www.microsoft.com/download/en/details.aspx?id=4865 and install it an the problem and the good PC. Then take a packet capture of a successfull attempt to access a share and of an unsuccesfull attempt and look through them to see where the error occurs. Further things to check - what are the bindings of the Client for MS networks on the problem PC and the good PC in comparison to the bindings of the File and Printer Sharing for MS networks. ( These bindings you find under Advanced settings in the Advanced Menu of the Network Connections (Adapter settings) page ) Wolfgang

Your hardware all seems fine Problem seems to be software settings for Permissions A bit more background might be useful Win 7 Version? Update status? Fully updated? If so via Win Update or occassional? Problem Scenario - new on m/c that previously worked OK or recent new m/c that has failed to work properly? Server software - via Homegroup or do you have something else? Anti virus software? Firewall? You said disabled. Is that just W7 or is there another? Perhaps a bit late to ask this but What is your preferred objective? Get a working setup as soon as possible or troubleshoot the problem to determine the cause (if possible) ie take time to do maybe many separate steps? Depending on your Problem Scenario you will of course have varying choices. Possible next steps Optional but in the interests of simplicity I suggest that you disable the WiFi adapter Remove problem-pc from the Homegroup (assuming this is not the Controller) Turn off the problem-pc Reboot the m/c that Controls the Homegroup Restart the problem-pc and (re)join the Homegroup (everything at Default)

Okay I think it is time to start packet captures. Download MS Network Monitor http://www.microsoft.com/download/en/details.aspx?id=4865 and install it an the problem and the good PC. Then take a packet capture of a successfull attempt to access a share and of an unsuccesfull attempt and look through them to see where the error occurs. The Network Monitor will not install on my problem pc - it starts up, asks me if i want to continue... i click 'yes' and that is 'all she wrote' - my mouse pointer goes back to arrow and NOTHING changed. It installed fine on the other PC. Tried running it 'as Administrator' - same result. Downloaded it several times to make sure it was not a corrupted d/l.

Win 7 Home Premium Service Pack 1 Fully updated, occasional. Excuse my ignorance - m/c? The network used to work just fine and one day I got this 'you may not have permission...' error. I do not recall making any specific changes. I do not use the network too frequently, more in spurts, but I recently added a media pc that hosts all music and video - aggravating not to be able to get to it with my main computer (problem pc) Homegroup is set up, but I used network shares before I set up the Homegroup. Not sure about a special 'server', just a peer-to-peer, I think (sorry not an expert on this) No AV software (at the moment) and no third party firewall, W7 firewall is disabled. Preference: Just get stuff going - as long as i can see all shared folders on my main PC and get to their content, I do not care how I get there. Re. Next steps: WIFI is generally disabled - I just turned it on for a bit to see if maybe the NIC was to blame. Used to be homegroup controller. I 'killed off' that homegroup, and used the new media pc as a controller.... no change

elwood0000 wrote: Okay I think it is time to start packet captures. Download MS Network Monitor http://www.microsoft.com/download/en/details.aspx?id=4865 and install it an the problem and the good PC. Then take a packet capture of a successfull attempt to access a share and of an unsuccesfull attempt and look through them to see where the error occurs.   The Network Monitor will not install on my problem pc - it starts up, asks me if i want to continue... i click 'yes' and that is 'all she wrote' - my mouse pointer goes back to arrow and NOTHING changed. It installed fine on the other PC. Tried running it 'as Administrator' - same result. Downloaded it several times to make sure it was not a corrupted d/l. That's very strange and would in my opinion indicates a corrupt network stack. Either you have a program installed, which interferes with the Windows networking stack or it has gotten corrupt in some other way. You could try to remove all network cards from your PC by unplugging all network cables, dectivating them and uninstalling them via Device manager. Then reboot, there should be no network available at all. Reboot a second time and activate your network card - that way the network stack should be reinstalled and if you are lucky, you should then be able to install Network monitor and maybe your connectivity problems are solved, too. BTW is the Client for MS networks bound to IPv6 and IPv4 ? Wolfgang

OK - sorry about my poor abreviation for machine! Is it possible date wise that the problem followed after your new media pc? I had thought that possibly a system restore would be appropriate but it is unlikely where there have been changes involving more than one machine. Instead I suggest a reconfiguration to establish a known baseline, as follows:- Remove all shares from all pcs. Remove Homegroup from all pcs. Turn off all pcs. Choose a pc to be your HomeGroup controller (I suggest your main pc) and create a new HomeGroup Start another computer and join the new Homegroup. Test and proceed to the next pc if OK. I suggest to leave the media pc to be last. At this stage you will hopefully have a working HomeGroup. If so there is no need to create network shares as W7 will handle things just fine. Fingers crossed!

You could try to remove all network cards from your PC by unplugging all network cables, dectivating them and uninstalling them via Device manager. Then reboot, there should be no network available at all. Reboot a second time and activate your network card - that way the network stack should be reinstalled and if you are lucky, you should then be able to install Network monitor and maybe your connectivity problems are solved, too. BTW is the Client for MS networks bound to IPv6 and IPv4 ? Wolfgang no such luck - i did exactly that the other day..... even reset the router to give it a fresh start too.... how would i figured out the MS Network binding? all i can do is set or take off a check-mark......

OK - sorry about my poor abreviation for machine! Is it possible date wise that the problem followed after your new media pc? I had thought that possibly a system restore would be appropriate but it is unlikely where there have been changes involving more than one machine. Instead I suggest a reconfiguration to establish a known baseline, as follows:- Remove all shares from all pcs. Remove Homegroup from all pcs. Turn off all pcs. Choose a pc to be your HomeGroup controller (I suggest your main pc) and create a new HomeGroup Start another computer and join the new Homegroup. Test and proceed to the next pc if OK. I suggest to leave the media pc to be last. At this stage you will hopefully have a working HomeGroup. If so there is no need to create network shares as W7 will handle things just fine. Fingers crossed! been there, done that, bought the t-shirt to prove it..... unfortunately...it did not fix anything...

been there, done that, bought the t-shirt to prove it..... unfortunately...it did not fix anything... That's hard to follow .. Are you saying that you could not get the first two pcs to work together satisfactorily using HomeGroup? Somewhere along the chain of events that I suggested there should be a change between success and failure. ps my earlier reference to shares should really have read network shares (to avoid confusion with sharing)

That's hard to follow .. Are you saying that you could not get the first two pcs to work together satisfactorily using HomeGroup? Somewhere along the chain of events that I suggested there should be a change between success and failure. ps my earlier reference to shares should really have read network shares (to avoid confusion with sharing) The Network works like a charm between all computers, whether as normal sharing or as homegroup, it also works like a charm with any computer accessing the problem pc. The ONLY thing that does not work is the problem PC accessing anything on the network.... I do not think the media pc has anything to do with the issue - it merely is the reason why I am using the network more than I used to.

The Network works like a charm between all computers, whether as normal sharing or as homegroup, it also works like a charm with any computer accessing the problem pc. The ONLY thing that does not work is the problem PC accessing anything on the network.... I do not think the media pc has anything to do with the issue - it merely is the reason why I am using the network more than I used to. Sorry but to me your second sentence contradicts the first. If you can't access a shared folder on pc2 from pc1 and they are both on the same HomeGroup then the HomeGroup isn't working! (Asuming there is a shared folder and it is shared for HomeGroup) Have you tried the elimination procedure that I suggested?

elwood0000 wrote:   You could try to remove all network cards from your PC by unplugging all network cables, dectivating them and uninstalling them via Device manager. Then reboot, there should be no network available at all. Reboot a second time and activate your network card - that way the network stack should be reinstalled and if you are lucky, you should then be able to install Network monitor and maybe your connectivity problems are solved, too. BTW is the Client for MS networks bound to IPv6 and IPv4 ? Wolfgang no such luck - i did exactly that the other day..... even reset the router to give it a fresh start too.... how would i figured out the MS Network binding? all i can do is set or take off a check-mark...... If the check-mark is checked it is bound to your network card, if it is unchecked it is not bound. There should be entries for IP4 and IP6 both at the File and Printer Sharing and at the Client and they should match. As a test I would bind both protocols to everything. Wolfgang

Sorry but to me your second sentence contradicts the first. If you can't access a shared folder on pc2 from pc1 and they are both on the same HomeGroup then the HomeGroup isn't working! (Asuming there is a shared folder and it is shared for HomeGroup) Have you tried the elimination procedure that I suggested? Well, yes, with strict semantics, it does contradict. To remove the contradiction, I should have stated that the Network works like a charm, except for the problem PC. The problem PC, when on the network also can be accessed, but cannot access anything else. Not sure what else to eliminate?

As a test I would bind both protocols to everything. I have no clue of how to achieve that..... ;) I only see one Client, one qos packet scheduler, one file and printer share, the two protocols IPv4 and IPv6, as well as a link layer topology discovery mapper i/o driver and a link layer topology discovery responder....

The problem PC, when on the network also can be accessed, but cannot access anything else. Not sure what else to eliminate? Slight change of tack - create a new User on the problem pc and test that out.

elwood0000 wrote:   As a test I would bind both protocols to everything. I have no clue of how to achieve that..... ;) I only see one Client, one qos packet scheduler, one file and printer share, the two protocols IPv4 and IPv6, as well as a link layer topology discovery mapper i/o driver and a link layer topology discovery responder....  If you see that you were before on a page, where you could select your network connection. If you are on this page (you get there by opening adapter settings from the Network and Sharings page) goto Organize / Layout and make a checkbox for Menu bar. That opens the menu bar for network settings like it was in WinXP. There in the Advanced Menu you will find the Advanced Settings, which show you Adapters and Bindings and Providerorder. Adapters and Bindings is what you are searching for. Further can you post the output of ipconfig -all (entered in a cmd-prompt) from the problem PC and from a working PC to see the differences between them. Wolfgang

Slight change of tack - create a new User on the problem pc and test that out. "no cigar" - new user [Admin], old problems....

IPv4 and v6 had everything bound. ipconfig /all Problem PC: Windows IP Configuration Host Name . . . . . . . . . . . . : problem-PC Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : Belkin Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : Belkin Description . . . . . . . . . . . : Broadcom NetLink (TM) Gigabit Ethernet Physical Address. . . . . . . . . : A4-BA-DB-E7-1C-9E DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IPv6 Address. . . . . . . . . . . : 2002:62f2:4af1:1234:7d28:8f9:4e72:9863(Pr eferred) Temporary IPv6 Address. . . . . . : 2002:62f2:4af1:1234:c0c0:1b75:77d7:1782(P referred) Link-local IPv6 Address . . . . . : fe80::7d28:8f9:4e72:9863%29(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.2.2(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Lease Obtained. . . . . . . . . . : Wednesday, November 09, 2011 7:23:48 PM Lease Expires . . . . . . . . . . : Friday, November 06, 2020 7:23:47 PM Default Gateway . . . . . . . . . : fe80::222:75ff:fed4:59ac%29 192.168.2.1 DHCP Server . . . . . . . . . . . : 192.168.2.1 DHCPv6 IAID . . . . . . . . . . . : 497335003 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-13-1D-AA-9A-A4-BA-DB-E7-1C-9E DNS Servers . . . . . . . . . . . : 192.168.2.1 192.168.2.1 NetBIOS over Tcpip. . . . . . . . : Enabled Wireless LAN adapter Wireless Network Connection: Connection-specific DNS Suffix . : Belkin Description . . . . . . . . . . . : DW1525 (802.11n) WLAN PCIe Card Physical Address. . . . . . . . . : C4-17-FE-81-01-86 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IPv6 Address. . . . . . . . . . . : 2002:62f2:4af1:1234:11c4:b285:cacc:7575(P referred) Temporary IPv6 Address. . . . . . : 2002:62f2:4af1:1234:b527:88d7:d706:64b(Pr eferred) Link-local IPv6 Address . . . . . : fe80::11c4:b285:cacc:7575%10(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.2.9(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Lease Obtained. . . . . . . . . . : Wednesday, November 09, 2011 7:13:16 PM Lease Expires . . . . . . . . . . : Tuesday, November 10, 2020 4:09:00 PM Default Gateway . . . . . . . . . : fe80::222:75ff:fed4:59ac%10 192.168.2.1 DHCP Server . . . . . . . . . . . : 192.168.2.1 DHCPv6 IAID . . . . . . . . . . . : 197400574 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-13-1D-AA-9A-A4-BA-DB-E7-1C-9E DNS Servers . . . . . . . . . . . : 192.168.2.1 192.168.2.1 NetBIOS over Tcpip. . . . . . . . : Enabled Tunnel adapter isatap.Belkin: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Belkin Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3 Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Tunnel adapter Teredo Tunneling Pseudo-Interface: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:2801:d45:3f57:fdfd(Prefe rred) Link-local IPv6 Address . . . . . : fe80::2801:d45:3f57:fdfd%11(Preferred) Default Gateway . . . . . . . . . : NetBIOS over Tcpip. . . . . . . . : Disabled Tunnel adapter isatap.{F4D6658C-F515-4BA6-ABB9-522B3C46D531}: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2 Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Tunnel adapter Local Area Connection* 14: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft ISATAP Adapter #4 Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes

Windows IP Configuration Host Name . . . . . . . . . . . . : Good-PC Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : Belkin Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : Belkin Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connection Physical Address. . . . . . . . . : 00-1D-60-9C-44-D5 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IPv6 Address. . . . . . . . . . . : 2002:62f2:4af1:1234:404:360f:d0fe:5cf1(Pr eferred) Temporary IPv6 Address. . . . . . : 2002:62f2:4af1:1234:c077:7a7:6e9e:f25d(Pr eferred) Link-local IPv6 Address . . . . . : fe80::404:360f:d0fe:5cf1%10(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.2.11(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Lease Obtained. . . . . . . . . . : Thursday, November 10, 2011 3:21:57 AM Lease Expires . . . . . . . . . . : Sunday, November 08, 2020 7:32:18 PM Default Gateway . . . . . . . . . : fe80::222:75ff:fed4:59ac%10 192.168.2.1 DHCP Server . . . . . . . . . . . : 192.168.2.1 DHCPv6 IAID . . . . . . . . . . . : 234888544 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-BB-11-24-00-1D-60-9C-44-D5 DNS Servers . . . . . . . . . . . : 192.168.2.1 192.168.2.1 NetBIOS over Tcpip. . . . . . . . : Enabled Tunnel adapter isatap.Belkin: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft ISATAP Adapter Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Tunnel adapter Local Area Connection* 11: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:3425:2ec5:9d0d:b50e(Pref erred) Link-local IPv6 Address . . . . . : fe80::3425:2ec5:9d0d:b50e%12(Preferred) Default Gateway . . . . . . . . . : NetBIOS over Tcpip. . . . . . . . : Disabled

elwood0000 wrote: IPv4 and v6 had everything bound. ipconfig /all Problem PC: Windows IP Configuration      Host Name . . . . . . . . . . . . : problem-PC    Primary Dns Suffix  . . . . . . . :    Node Type . . . . . . . . . . . . : Hybrid    IP Routing Enabled. . . . . . . . : No    WINS Proxy Enabled. . . . . . . . : No    DNS Suffix Search List. . . . . . : Belkin   Ethernet adapter Local Area Connection:      Connection-specific DNS Suffix  . : Belkin    Description . . . . . . . . . . . : Broadcom NetLink (TM) Gigabit Ethernet    Physical Address. . . . . . . . . : A4-BA-DB-E7-1C-9E    DHCP Enabled. . . . . . . . . . . : Yes    Autoconfiguration Enabled . . . . : Yes    IPv6 Address. . . . . . . . . . . : 2002:62f2:4af1:1234:7d28:8f9:4e72:9863(Pr eferred)    Temporary IPv6 Address. . . . . . : 2002:62f2:4af1:1234:c0c0:1b75:77d7:1782(P referred)    Link-local IPv6 Address . . . . . : fe80::7d28:8f9:4e72:9863%29(Preferred)    IPv4 Address. . . . . . . . . . . : 192.168.2.2(Preferred)    Subnet Mask . . . . . . . . . . . : 255.255.255.0    Lease Obtained. . . . . . . . . . : Wednesday, November 09, 2011 7:23:48 PM    Lease Expires . . . . . . . . . . : Friday, November 06, 2020 7:23:47 PM    Default Gateway . . . . . . . . . : fe80::222:75ff:fed4:59ac%29                                        192.168.2.1    DHCP Server . . . . . . . . . . . : 192.168.2.1    DHCPv6 IAID . . . . . . . . . . . : 497335003    DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-13-1D-AA-9A-A4-BA-DB-E7-1C-9E      DNS Servers . . . . . . . . . . . : 192.168.2.1                                        192.168.2.1    NetBIOS over Tcpip. . . . . . . . : Enabled   Wireless LAN adapter Wireless Network Connection:      Connection-specific DNS Suffix  . : Belkin    Description . . . . . . . . . . . : DW1525 (802.11n) WLAN PCIe Card    Physical Address. . . . . . . . . : C4-17-FE-81-01-86    DHCP Enabled. . . . . . . . . . . : Yes    Autoconfiguration Enabled . . . . : Yes    IPv6 Address. . . . . . . . . . . : 2002:62f2:4af1:1234:11c4:b285:cacc:7575(P referred)    Temporary IPv6 Address. . . . . . : 2002:62f2:4af1:1234:b527:88d7:d706:64b(Pr eferred)    Link-local IPv6 Address . . . . . : fe80::11c4:b285:cacc:7575%10(Preferred)    IPv4 Address. . . . . . . . . . . : 192.168.2.9(Preferred)    Subnet Mask . . . . . . . . . . . : 255.255.255.0    Lease Obtained. . . . . . . . . . : Wednesday, November 09, 2011 7:13:16 PM    Lease Expires . . . . . . . . . . : Tuesday, November 10, 2020 4:09:00 PM    Default Gateway . . . . . . . . . : fe80::222:75ff:fed4:59ac%10                                        192.168.2.1    DHCP Server . . . . . . . . . . . : 192.168.2.1    DHCPv6 IAID . . . . . . . . . . . : 197400574    DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-13-1D-AA-9A-A4-BA-DB-E7-1C-9E      DNS Servers . . . . . . . . . . . : 192.168.2.1                                        192.168.2.1    NetBIOS over Tcpip. . . . . . . . : Enabled   Tunnel adapter isatap.Belkin:      Media State . . . . . . . . . . . : Media disconnected    Connection-specific DNS Suffix  . : Belkin    Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3    Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0    DHCP Enabled. . . . . . . . . . . : No    Autoconfiguration Enabled . . . . : Yes   Tunnel adapter Teredo Tunneling Pseudo-Interface:      Connection-specific DNS Suffix  . :    Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface    Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0    DHCP Enabled. . . . . . . . . . . : No    Autoconfiguration Enabled . . . . : Yes    IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:2801:d45:3f57:fdfd(Prefe rred)    Link-local IPv6 Address . . . . . : fe80::2801:d45:3f57:fdfd%11(Preferred)    Default Gateway . . . . . . . . . :    NetBIOS over Tcpip. . . . . . . . : Disabled   Tunnel adapter isatap.{F4D6658C-F515-4BA6-ABB9-522B3C46D531}:      Media State . . . . . . . . . . . : Media disconnected    Connection-specific DNS Suffix  . :    Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2    Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0    DHCP Enabled. . . . . . . . . . . : No    Autoconfiguration Enabled . . . . : Yes   Tunnel adapter Local Area Connection* 14:      Media State . . . . . . . . . . . : Media disconnected    Connection-specific DNS Suffix  . :    Description . . . . . . . . . . . : Microsoft ISATAP Adapter #4    Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0    DHCP Enabled. . . . . . . . . . . : No    Autoconfiguration Enabled . . . . : Yes First I'd remove or disable the wireless adapter, because having two connections with the same name and different IP-addresses isn't a good solution. Then as a test I'd try to go only IPv6 or only IPv4 on all PCs to see if that changes your problem. If that does not help you have probably something unknown in your setup (maybe some third party application), which interferes whith your network connectivity. That the setup looks correct and that you cannot install MS Network monitor are indications in this direction. I'd try a repair of Windows and if that does net help I think you should reinstall your problem PC from scratch. Afterwards - before installing any additional software - test your connectivity, that should work. Then you can start reinstalling your software each individually and setting a restore point before each installation, then you can test after which installation your connectivity is disturbed. Wolfgang

I HAVE THIS SAME PROBLEM!!!.... I have this problem right now but when connecting a client computer to VPN. Whenever I ping anything on the network, it resolves to 207.223.0.140. When I ping anything, it gives me this IP. When I do a nslookup locally, it gives me this IP. I am completely lost right now. Could this be a virus? I have tried everything. The VPN works company wide, and this is only a single computer that is having this problem.

ravi.patel wrote: I HAVE THIS SAME PROBLEM!!!.... I have this problem right now but when connecting a client computer to VPN.  Whenever I ping anything on the network, it resolves to 207.223.0.140.  When I ping anything, it gives me this IP.  When I do a nslookup locally, it gives me this IP.  I am completely lost right now.  Could this be a virus?  I have tried everything.  The VPN works company wide, and this is only a single computer that is having this problem.     No, that is no virus but the internet address, which your ISP (Comcast) serves to you for every unknown dns-address. As the ISP probably won't know your local addresses and names, every lookup for your local names, made to your ISP, will result in that address. You would have to set the dns-server via VPN to your internal dns-server instead - or use a local hosts file containing names and addresses of your VPN accessible computers to resolve this issue. Wolfgang

The "client for microsoft networks" is not installed in the network adapter. I had the same problem and this was the fix. Cptspig <o:p></o:p>

The "client for microsoft networks" is not installed in the network adapter. I had the same problem and this was the fix. Cptspig

thank you so much i was tryna figure out why i could not access my pc i went to local area connections and client for Microsoft was missing install it and poof it worked thank uu